AVEVA™ Historian Client Readme

AVEVA Historian Client 2020 R2

Last revision: 11/24/2020

About This Readme

This Readme provides information about AVEVA Historian Client 2020 R2.

For information about using the product, see the AVEVA Historian documentation.

New Features In This Release

The AVEVA Historian Client 2020 R2 release includes these features:

• Trend supports UOM conversion

  Note: 32-bit operating systems are no longer supported

Known Issues in This Release

Under certain circumstances, when migrating a CAB file to AVEVA System Platform 2020 from an older galaxy that contains ArchestrA Graphics and utilizes the Historical Trend control, the migration may stall at some point and fail to complete. No error message will be displayed.

Workaround:

1. Create a backup of the existing galaxy
2. Save a copy of the following Historian Client binaries from an installation of AVEVA System Platform matching the version your galaxy is migrating from:
   • %ProgramFiles(x86)%\Common Files\ArchestrA\aaHistClientDatabase.dll
   • %ProgramFiles(x86)%\Common Files\ArchestrA\aaAFCommonTypes.dll
   • %ProgramFiles(x86)%\Common Files\ArchestrA\aaHistClientUtil.dll
3. Install AVEVA System Platform 2020
4. Open the System Platform IDE
5. Create a new galaxy with the same name as the previous galaxy, selecting the default_empty.cab type
6. Close the IDE
7. Copy the binaries saved from the previous version of AVEVA System Platform (from step 2) to %ProgramFiles(x86)%\Common Files\ArchestrA\Framework\Bin
8. Open aaSMC and restore the galaxy
9. Open the System Platform IDE and connect to the galaxy, completing the migration.

   Note: After successful migration, there may be errors reported from the aahEventEnum and aahEventSvc components, and warnings from the aahReplication component. These errors and warnings can be ignored.

Resolved Issues In This Release

This section describes issues resolved in the AVEVA Historian Client 2020. These issues are listed by their Change Request (CR) number and any assigned Service Request (SR) number. The left column of the table shows the original Change Request in which the issue was identified. The Related Change Requests column lists other change requests that are related to the original change request.